View Issue Details

IDProjectCategoryView StatusLast Update
0001266T99X171.00 SKB EagleSW Issuepublic2021-09-30 10:39
Reporter(ALTech) Younkwang Jung Assigned To(SW) Kerwin Chen Due Date
PrioritynormalSeveritys2-severeReproducibilityhave not tried
Status closedResolutionfixed 
Summary0001266: [Smart3][BTF] Black screen issue after wakeup
DescriptionHi Kerwin

I registered this issue with Jira first.
jira link is
https://jira.skbroadband.com/browse/BTFAML-689

FW : v15.524.10
Test method : Vod Test script (new_CH-VOD-SENIER-ZEM_Youtube_Sleep_aging_0402.sh)

STB entered sleep mode at 13:33:37 and wakup at 13:33:53.
The problem is that the screen has been continuously black screen since wakeup.

After this issue occurred, I unplugged and plugged in the HDMI cable, and the video output is working properly again.
(It looks like an issue related to HDMI.)

I don't see any special clues yet.
Please check the log.

Thank you
YK.Jung
TagsNo tags attached.
Attach Tags

Users monitoring this issue

User List (ALTech) SY Yoon , (SW) Brent Choi , (SW) Jerry Lin

Activities

(ALTech) Younkwang Jung

2021-06-07 08:52

developer  

logcat.log.zip (2,560,760 bytes)
Serial-COM4_0604_000003.log (12,504,840 bytes)

(SW) Kerwin Chen

2021-06-08 10:32

developer   ~0007390

Hi Mr. YK. Jung,

Do you have other log files ?
From logcat.log.0001, Android VM seems restart very frequently.
Android system may have problem more earlier.
You can see process ID of AndroidRuntime changing from log below

========= logcat.log.0001 =========
06-04 13:05:29.197 31381 31381 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
06-04 13:05:29.204 31381 31381 I AndroidRuntime: Using default boot image
06-04 13:05:29.204 31381 31381 I AndroidRuntime: Leaving lock profiling enabled
06-04 13:05:29.464 31381 31381 D AndroidRuntime: Calling main entry com.android.commands.input.Input
06-04 13:05:29.476 31381 31381 D AndroidRuntime: Shutting down VM
06-04 13:05:30.977 31397 31397 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
06-04 13:05:30.985 31397 31397 I AndroidRuntime: Using default boot image
06-04 13:05:30.985 31397 31397 I AndroidRuntime: Leaving lock profiling enabled
06-04 13:05:31.256 31397 31397 D AndroidRuntime: Calling main entry com.android.commands.input.Input
06-04 13:05:41.803 31492 31492 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
06-04 13:05:41.813 31492 31492 I AndroidRuntime: Using default boot image
06-04 13:05:41.813 31492 31492 I AndroidRuntime: Leaving lock profiling enabled
06-04 13:05:42.083 31492 31492 D AndroidRuntime: Calling main entry com.android.commands.input.Input
06-04 13:05:42.102 31492 31492 D AndroidRuntime: Shutting down VM
06-04 13:09:32.222 32065 32065 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
06-04 13:09:32.228 32065 32065 I AndroidRuntime: Using default boot image
06-04 13:09:32.229 32065 32065 I AndroidRuntime: Leaving lock profiling enabled
06-04 13:09:32.474 32065 32065 D AndroidRuntime: Calling main entry com.android.commands.input.Input
06-04 13:09:32.488 32065 32065 D AndroidRuntime: Shutting down VM
06-04 13:10:36.185 368 368 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
06-04 13:10:36.194 368 368 I AndroidRuntime: Using default boot image
06-04 13:10:36.194 368 368 I AndroidRuntime: Leaving lock profiling enabled
06-04 13:10:36.556 368 368 D AndroidRuntime: Calling main entry com.android.commands.input.Input
06-04 13:11:50.969 708 708 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
06-04 13:11:50.976 708 708 I AndroidRuntime: Using default boot image
06-04 13:11:50.977 708 708 I AndroidRuntime: Leaving lock profiling enabled
06-04 13:11:51.224 708 708 D AndroidRuntime: Calling main entry com.android.commands.input.Input
06-04 13:11:51.240 708 708 D AndroidRuntime: Shutting down VM
06-04 13:15:02.530 865 865 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
06-04 13:15:02.539 865 865 I AndroidRuntime: Using default boot image
06-04 13:15:02.539 865 865 I AndroidRuntime: Leaving lock profiling enabled
06-04 13:15:02.809 865 865 D AndroidRuntime: Calling main entry com.android.commands.input.Input
06-04 13:15:02.820 865 865 D AndroidRuntime: Shutting down VM

(ALTech) Younkwang Jung

2021-06-23 10:11

developer   ~0007533

Last edited: 2021-06-23 10:12

View 2 revisions

Hi Kerwin

The shutdown vm value is occurring when input key evnet occurs.
This is not an issue. please check attached file

This issue seems to occur as a whole, including VoC.
and it does not occur in FW on February 9th (usb_bfx-at100_V15.522.56) . It could be related to HDMI.

I also reported to Amlogic. we need to find a solution to this issue as soon as possible.

Thank you
YK.Jung

Issue History

Date Modified Username Field Change
2021-06-07 08:52 (ALTech) Younkwang Jung New Issue
2021-06-07 08:52 (ALTech) Younkwang Jung Status new => assigned
2021-06-07 08:52 (ALTech) Younkwang Jung Assigned To => (SW) Kerwin Chen
2021-06-07 08:52 (ALTech) Younkwang Jung File Added: new_CH-VOD-SENIER-ZEM_Youtube_Sleep_aging_0402.zip
2021-06-07 08:52 (ALTech) Younkwang Jung File Added: logcat.log.zip
2021-06-07 08:52 (ALTech) Younkwang Jung File Added: Serial-COM4_0604_000003.log
2021-06-07 08:52 (ALTech) Younkwang Jung File Added: 이슈_2021_06_04_10_50_07_8 (2).mp4
2021-06-07 08:53 (ALTech) Younkwang Jung Issue Monitored: (SW) Brent Choi
2021-06-07 08:53 (ALTech) Younkwang Jung Issue Monitored: (SW) Jerry Lin
2021-06-07 08:53 (ALTech) Younkwang Jung Issue Monitored: (ALTech) SY Yoon
2021-06-08 10:32 (SW) Kerwin Chen Note Added: 0007390
2021-06-23 10:11 (ALTech) Younkwang Jung File Added: image-2021-05-12-20-11-01-539.png
2021-06-23 10:11 (ALTech) Younkwang Jung Note Added: 0007533
2021-06-23 10:12 (ALTech) Younkwang Jung Note Edited: 0007533 View Revisions
2021-09-30 10:39 (ALTech) Younkwang Jung Status assigned => closed
2021-09-30 10:39 (ALTech) Younkwang Jung Resolution open => fixed